Repository navigation
Prepare Miden integration example for mainnet - #17
Abhimanyu121 wants to merge 6 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
React Doctor found 2 new issues in 1 file · 2 warnings · score 83 / 100 (Needs work) · 0 fixed · vs 2 warnings
Reviewed by React Doctor for commit |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
|
||
| useEffect(() => { | ||
| if (previousMidenAccountId.current !== midenAccountId) { | ||
| setLocalMidenNote(undefined); |
There was a problem hiding this comment.
React Doctor · react-doctor/no-adjust-state-on-prop-change (warning)
This effect adjusts state after a prop changes, so users briefly see the stale value.
Fix → Remove the adjustment effect by deriving values during render, resetting the component with a key, or updating related state in the event that changes the prop. Avoid tracking the previous prop in more state, which preserves the duplication. See https://react.dev/learn/you-might-not-need-an-effect#adjusting-some-state-when-a-prop-changes
Summary
Verification
pnpm typecheckpassedpnpm buildpassedThe pre-commit lint-staged command treats the existing test file as an ESLint warning because it has no matching ESLint config. Formatting and ESLint for the production source were checked directly before commit.